[Beta] Mint an MCP token for a Devbox.
[Beta] Mint a token that lets a running Devbox reach an upstream MCP (Model Context Protocol) server through the Runloop MCP hub, using the credential in the supplied secret. Tool access is limited to the MCP config’s allowed_tools, and the credential itself is never exposed to the Devbox.
The token is bound to this Devbox and is only accepted for requests that originate from it. Nothing is stored on the Devbox: the token is returned to the caller and is not re-issued when the Devbox is resumed.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The Devbox ID.
Body
[Beta] Parameters for minting an MCP token for a Devbox. The token grants the Devbox access to the upstream MCP server described by the MCP config, using the supplied credential, with tool-level access control based on the config's allowed_tools.
Response
MCP token minted successfully.
The Devbox the token is bound to.
The ID of the MCP config the token grants access to.
The token to send to the MCP hub as a Bearer token in the Authorization header. Only accepted for requests originating from the bound Devbox.
The MCP hub URL the token authenticates against. Matches the RL_MCP_URL environment variable inside the Devbox.
The upstream MCP server endpoint the hub proxies to.
Glob patterns for the tools the token permits.
